Example: Configuration for file system-based loading (Java and .NET)

The following is an example of the application.properties file, configuring Oracle Web Determinations to load everything from the file system.

The following assumes that the Java version of the application is being run, and the resources are placed into folders called configuration, images, properties, resources, rulebases and templates under the WEB-INF/classes folder in the web application's deployment folder.

Notes:

The following will not work under Java for application servers that do not explode the WAR (for example, WebLogic) - in this case, the only option available is to use classpath-based resource loading.
Under .NET, the paths to the resources must be changed to the relative paths under the application's directory; for example, 'bin/rulebases', 'bin/configuration' and so on.

The cache.loaded.rulebases=false property, combined with the fact that we are loading the rulebases from the file system, will cause a directory watcher to be invoked on the rulebases directory. This allows rulebases to be dynamically loaded, removed and updated as the contents of the rulebases directory changes.

#########################################
# Core application properties, these are used to configure the application and are not available to
# screens.
#########################################
# The locale to default to if we're displaying a screen that is not attached to a specific locale.
default.locale =en-US
# Set enable.debugger to true if you need to be able to debug from Oracle Policy Modeling
enable.debugger =true

#########################################
# Rulebase Loading Properties

# If rulebases are to be loaded as resource streams, this
# property specified whether or not the Java classpath
# is to be used to load the resources.
load.rulebase.from.classpath =false

rulebase.path =/WEB-INF/classes/rulebases
cache.loaded.rulebases =false
enable.second.person =true

# Screens file content can include html authored by users in oracle policy modelling as static content.
# These options determine whether to scan the content at application start time and verify that the
# tags deployed in the rulebase are in the whitelist of allowable content.
screens.validate.html =true
# any tag not on this list will cause an exception to be thrown during rulebase loading and the rulebase will not be available.
# if additional tags are required they must be added to this list.
screens.html.tags.whitelist =b;i;del;s;div;p;span;pre;table;td;tr;ol;ul;li;blockquote;font;a;h1;h2;h3;h4;h5;h6;img;hr;br;u

#########################################
# Resourcing Properties
load.messages.as.resource =true
messages.path =configuration
cache.messages =true

load.images.as.resource =true
images.path =images
cache.images =true

load.resource.as.resource =true
resources.path =resources
cache.resources =true

load.properties.as.resource =true
properties.path =configuration
cache.properties =false

load.templates.as.resource =true
templates.path =templates
cache.templates =false

load.static.content.as.resource =false
static.content.path =content

#########################################
# Plugins Properties
# This is a java only property used for web application servers where class path introspection is not possible
# such as WebLogic when the war file is not exploded. In that case, this property contains the ';' list of fully qualified
# plugin classes to load and the plugin libraries must reside in a directory that will automatically loaded on the classpath

plugin.libraries =

Example: Configuration for file system-based loading (Java and .NET)

See also: